Okta Workflows (Azuqua)

We use it to keep record of customer's accounts, the contact each customer mades when he reaches out to us, to created cases related to customer contacts, which are typically about concerns or issues they experience, we use it to take chats, calls, emails, etc.

We are currently using Azuqua to make an automated connection between Smartsheet and our Dynamics 365 CRM. Azuqua pulls data from each, verifies, then updates. This allows our other departments to freely share information with sales and for us to leverage CRM for customer service needs without requiring manual modification.

Azuqua is being used by the IT department to automate tasks primarily in Smartsheet. In addition, there are many limitations in Smartsheet, so Azuqua provides a background extension to Smartsheet functionality (e.g.: automatically cleaning out old discussions/comments, providing cell update timestamps, and other tasks using webhooks and API calls).

We are leveraging Azuqua to bridge the disconnect between Zendesk, Jira, and Salesforce. All of them have integrations to one another but are lacking which is where Azuqua comes into play. I am certain that we've only scratched the surface with what Azuqua can do and can not wait to continue leveraging this product for other use cases. Other departments across the organization are already using this and will continue to grow.

We use many applications to run a department responsible for Marketing assets within my company. We have approximately 200 people and support a company of 150k people.

Many of these applications are running independently and efforts to integrate them require custom implementation of interfacing projects. Once done, the tools also need to be hosted on some sort of infrastructure.

Azuqua provides a perfect solution for this challenge as they allow GUI-based connectivity with wide range of logical functions to map the data and functions. Since we don't store any data on Azuqua's end (data transitions are transient), there is also very low security risk. As a bonus, we don't need to host any infrastructure.

Our use of Azuqua filled a niche need in our workflow. We were using Smartsheet forms to capture support requests, and use Salesforce as our CRM. Smartsheet does not have a real way of connecting the two. Azuqua made it simple to turn the form entries into a support case. In minutes I was able to set it up and had cases being assigned to the proper contacts, or had those contacts it created. Azuqua was a great help in getting this set up as well.

Before we used Azuqua, we were spending an average of 2 hours per day just creating these tickets. Saving 10 hours a week was an easy decision to make.

In the service of a Digital Asset Management system and complementary Project Management tool, Azuqua is employed for API calls between separate databases to automate function triggers within the integrated tools.

The Azuqua platform originally was purchased by the services team to solve business requirements related to automated workflow and system integration. The success of the Azuqua platform within services attracted the IT team to the product who have since leveraged it across the whole organization including system critical processing.

We use Azuqua for a few major business problems we needed to be addressed:

• Salesforce to Workfront - Accounts and Contact information
• Salesforce to Workfront - Opportunity (Products) to Workfront Projects (2 way)
• Salesforce to Google - Client folder creation for our 5k + clients / prospects
• Mailgun to Workfront - Addressing Workfront's email ingestion process was not sufficient for us as they miss emails which isn't ok for us
• Workfront to Customer Thermometer - Surveys automatically sent out to clients to address any client issues they have with the way we solve problems

We use this across our organization. Salesforce is now our one authoritative place for all CRM information. Before we had one source, but we had multiple targets that were never in sync with our authoritative system, that problem is now gone.

The second major issue that is solved now is our sales to operations team process is automated. When a sale is made a project is automatically created for our operations team to address; this solves an unreal amount of communication issues we had between the two sides of our business.

We onboarded Azuqua to connect Google services with our project management software in our marketing department. We then scaled it across several other projects supporting other teams as we utilized other SaaS solutions. We were able to connect 2 disparate systems to send data from one to the other, eliminating duplicate data entry as well as keeping information in sync. By utilizing Azuqua we were also able to connect our DAM system to also be integrated. It has allowed us to be nimble as well as look avoid looking for that one tool solution in our tools ecosystem so that we can custom tailed our tech stack to our needs and connect them through Azuqua.